-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: [FC-0074] add note about decisions documented in each hooks repositories #662
base: master
Are you sure you want to change the base?
Conversation
Thanks for the pull request, @mariajgrimaldi! This repository is currently maintained by @sarina. Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.
|
99934df
to
9e16cf0
Compare
9e16cf0
to
8e1b831
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some ideas to see what you both think.
@@ -475,10 +475,16 @@ Having a clearly defined set of events would allow for simpler third party | |||
integration in areas like student learner event processing and course catalog | |||
management. | |||
|
|||
------------ | |||
|
|||
.. note:: All future decisions related to :doc:`Open edX Events <openedx-events:index>` that adhere to these guidelines for asynchronous event messaging will now be documented and made publicly available through the Architectural Decision Records (ADRs) in :doc:`Open edX Events ADRs <openedx-events:decisions/index>`. This includes decisions regarding the Event Bus, schema format, serialization, evolution, and design practices for event-driven architecture. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reading this gave me additional ideas that you may like or not like.
- This reads like a small decision. I’m wondering if there could be a brief OEP that describes this decision named “Event Related Decision Records”, or “Event and Filter…” or “Hook, Event and Filter…” that details this change, and notes could point to this OEP?
- Maybe this won’t be the last time we choose a library repo for housing OEP-esque ADRs on a topic? We could consider updating OEP-19 with this as an option, or an OEP-19 sub ADR, and also list all the current cases as an index.
These are just ideas, and they could influence how we add the notes. That said, we could make these notes the first iteration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I disagree with this - I think that's adding too much process that no one will ultimately end up reading/needing. I think this note in the OEP is enough. I ran this by Feanil and Kyle and they agree with me, as well.
************** | ||
Change History | ||
************** | ||
|
||
2024-01-14: Added note about decisions related to Open edX Events being documented and made publicly available through the Architectural Decision Records (ADRs) in the repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There may be more places that warrant this change, but “the repository” is vague and by default might mean “this repository”, but it doesn’t.
2024-01-14: Added note about decisions related to Open edX Events being documented and made publicly available through the Architectural Decision Records (ADRs) in the repository. | |
2024-01-14: Added note about decisions related to Open edX Events being documented and made publicly available through the Architectural Decision Records (ADRs) in the openedx-events repository. |
Description
This PR adds notes about Open edX Events and Filters to event-driven-related OEPs and the Hooks Extension Framework OEP, specifying where to find architectural decisions about the framework. This PR addresses: openedx/openedx-events#438 (review)